Linking dynamic computer data protection to an external state

ABSTRACT

A data backup manager links data backup robustness to an external state. The data backup manager monitors the external state. Responsive to the external state, the data backup manager adjusts parameters controlling data backup, such as backup frequency, backup content, and backup retention time. The data backup manager can increase these parameters responsive to an increase in an external distress state level, and decrease them in response to a decrease in the external distress state level.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.10/934,615, filed on Sep. 2, 2004, which is incorporated by reference inits entirety.

TECHNICAL FIELD

This invention pertains generally to enabling dynamic computer dataprotection by linking backup with an external state.

BACKGROUND

Currently, computer data (for example, data stored on disk volumes) arebacked up either on pre-set schedules, or in the event of a knownimpending disaster (for example, a loss of power, an imminent flood,etc.). This leaves any new or modified data fully vulnerable betweenbackups, because it is not possible to recover data more recent than thelast executed backup.

On the other hand, each executed backup uses both computing cycles andstorage resources. Therefore, although backing up frequently is safer interms of data integrity, it can become very resource expensive.Traditionally, a compromise has been reached for each protected systemby balancing the time between backups (the window of vulnerability) andthe resources needed or available to perform or hold the backup data.

In contemporary computing environments, information from externalsources concerning the stability of the system is often available. Forexample, a malicious code threat assessment system can provideinformation regarding a current threat level. However, today's backupsystems do not leverage external states to enhance data backupmanagement.

What is needed are methods, systems and computer readable media toimprove backup management, by automatically adjusting the frequencyand/or data granularity of backups responsive to states external to thebackup system.

SUMMARY OF INVENTION

The present invention comprises methods, systems and computer readablemedia for linking data backup robustness to an external state. In someembodiments, a data backup manager monitors an external state (such as asecurity threat assessment or other distress level). Responsive to theexternal state, the data backup manager adjusted parameters controllingdata backup. The parameters to modify can include backup frequency,backup content, and backup retention time. The data backup manager canincrease these parameters responsive to an increase in an externaldistress state level, and decrease them in response to a decrease in theexternal distress state level. Thus, the data backup manager ties theallocation of resources devoted to data backup to anticipated need.

The features and advantages described in this disclosure and in thefollowing detailed description are not all-inclusive, and particularly,many additional features and advantages will be apparent to one ofordinary skill in the relevant art in view of the drawings,specification, and claims hereof. Moreover, it should be noted that thelanguage used in the specification has been principally selected forreadability and instructional purposes, and may not have been selectedto delineate or circumscribe the inventive subject matter, resort to theclaims being necessary to determine such inventive subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a high level overview of a systemfor performing some embodiments of the present invention.

FIG. 2 is a flowchart, illustrating steps for tuning the backup scheduleresponsive to an external distress state, according to one embodiment ofthe present invention.

FIG. 3 is a flowchart, illustrating steps for tuning the backup scheduleresponsive to an external distress state, according to anotherembodiment of the present invention.

FIG. 4 is a flowchart, illustrating steps for tuning the backup scheduleresponsive to an external distress state, according to yet anotherembodiment of the present invention.

The Figures depict embodiments of the present invention for purposes ofillustration only. One skilled in the art will readily recognize fromthe following discussion that alternative embodiments of the structuresand methods illustrated herein may be employed without departing fromthe principles of the invention described herein.

DETAILED DESCRIPTION

FIG. 1•illustrates a high level overview of a system 100 for performingsome embodiments of present invention. A data backup manager 101 runs ina computer 103, and modifies a backup schedule 105 (or in otherembodiments other backup characteristics) responsive to an externalstate, thereby linking backup robustness to an external state. It is tobe understood that although the data backup manager 101 is illustratedas a single entity, as the term is used herein a data backup manager 101refers to a collection of functionalities which can be implemented assoftware, hardware, firmware or any combination of the three. Where adata backup manager 101 is implemented as software, it can beimplemented as a standalone program, but can also be implemented inother ways, for example as part of a larger program, as a plurality ofseparate programs, or as one or more statically or dynamically linkedlibraries.

The data backup manager 101 monitors a state external to the backupsystem, such as an external distress state level state (for example, anexternal security threat assessment, an external computing resourceoverload assessment, an external software stability assessment, etc.).In some embodiments of the present invention, the data backup manager101 monitors an external state by receiving e-mails 107 (or other formsof electronic notification, for example, control signals) from anexternal source 109 (for example, a threat assessment system) regardingthe external state. In other embodiments, the data backup manager 101reads data (for example, a global variable, a buffer, a port) externalto the data backup manager 101 concerning the external state. Typically,such data is provided by an external source 109. It is to be understoodthat although the external source 109 in FIG. 1 is illustrated as beingexternal to the computer 103 on which the data backup manager 101resides (for example, elsewhere on a local or wide area network, on theInternet, etc.), in some embodiments the external source 109 is locatedon the same computer 103 as the data backup manager 101. The externalsource 109 and state are external to the data backup manager 101, butneed not be external to the physical computer 103 on which the databackup manager 101 executes.

As illustrated in FIG. 1, responsive to the external source, the databackup manager 101 modifies the backup schedule 105 by adjustingparameters such as the backup frequency 111, the content 113 to backupand/or the retention 115 time for executed backups. The data backupmanager 101 backups data 117 from the computer 103 to a storage medium119, on which it retains the data backups 121 for the scheduled amountof time. Note that the storage medium 119 in FIG. 1 is illustrated asbeing on the computer 103 on which the data backup manager 101 executes(for example, a disk drive or a tape in a local tape drive). Of course,in some embodiments, the storage medium 119 (or media 119) residesexternal to that computer 103, for example in the form of a magnetic oroptical medium located elsewhere on a local or wide area network, on theInternet, etc.

FIG. 2 is a flowchart, illustrating steps for the data backup manager101 tuning the backup schedule 105 responsive to an external distressstate, according to one embodiment of the present invention. Asillustrated in FIG. 2, the data backup manager 101 notes 201 an increasein the external distress level. Responsive to the external distressstate level increasing, the data backup manager 101 can increase 203 thescheduled backup frequency 111, increase 205 the amount of content 113to backup, and/or retain 207 executed backups 121 for longer periods oftime.

Increasing 203 the frequency of data backups 121 reduces the window ofvulnerability for stored data 117 during times of high threat. Also inthe event of a successful attack or system compromise, increasing 203,205, 207 backup frequency, depth and/or retention periods increases thepossibility of recovering unmodified or undamaged versions of the data117 as they existed before the failure.

FIG. 3 is a flowchart, illustrating steps for the data backup manager101 tuning the backup schedule 105 responsive to an external distressstate, according to another embodiment of the present invention. Thedata backup manager 101 notes 301 a decrease in the external distresslevel. Responsive to the decrease in the external distress level, thedata backup manager 101 can decrease 303 the scheduled backup frequency111, decrease 305 the amount of content to backup, and/or retain 207executed backups 121 for shorter periods of time. This saves storageand/or computational resources when threat levels are low.

FIG. 4 is a flowchart, illustrating steps for the data backup manager101 tuning the backup schedule 105 responsive to an external distressstate, according to yet another embodiment of the present invention. Asillustrated in FIG. 4, the data backup manager 101 can note 401 at anexternal threat level is substantially at a critical point. In response,the data backup manager 101 executes 403 an immediate data backup 121.Note that what constitutes a critical point is a variable design choice.

As will be understood by those familiar with the art, the invention maybe embodied in other specific forms without departing from the spirit oressential characteristics thereof. Likewise, the particular naming anddivision of the modules, managers, features, attributes, methodologiesand other aspects are not mandatory or significant, and the mechanismsthat implement the invention or its features may have different names,divisions and/or formats. Furthermore, as will be apparent to one ofordinary skill in the relevant art, the modules, managers, features,attributes, methodologies and other aspects of the invention can beimplemented as software, hardware, firmware or any combination of thethree. Of course, wherever a component of the present invention isimplemented as software, the component can be implemented as a script,as a standalone program, as part of a larger program, as a plurality ofseparate scripts and/or programs, as a statically or dynamically linkedlibrary, as a kernel loadable module, as a device driver, and/or inevery and any other way known now or in the future to those of skill inthe art of computer programming. Additionally, the present invention isin no way limited to implementation in any specific programminglanguage, or for specific operating system or environment. Accordingly,the disclosure of the present invention is intended to be illustrative,but not limiting, of the scope of the invention, which is set forth inthe following claims.

What is claimed is:
 1. A computer-implemented method of managing abackup system on a first computer, the method comprising the steps of:monitoring via a network, by a data backup manager on the firstcomputer, a distress state level of an external source that is distinctfrom the backup system on the first computer that backs up data storedon the first computer, the distress state level of the external sourcemonitored by the data backup manager based on a notification receivedfrom the external source, wherein the external source is executed on asecond computer that is distinct from the first computer that includesthe data backup manager, the second computer does not back up the datastored on the first computer; noting, by the data backup manager on thefirst computer, a change to the distress state level of the externalsource indicating a security threat at the external source based on themonitored distress state level of the external source; automaticallyadjusting, by the data backup manager on the first computer, a backupschedule of the backup system on the first computer based on the notedchange to the external distress state level of the external sourceindicating the security threat at the external source, wherein theadjusting the backup schedule comprises adjusting an amount of contenton the first computer to back up based on the noted change to theexternal distress state level of the external source; and performing, bythe data backup manager on the first computer, a backup of the datastored on the first computer according to the adjusted backup schedule.2. The computer-implemented method of claim 1, wherein automaticallyadjusting the backup schedule further comprises: adjusting a frequencyof backing up content on the backup system based on the distress statelevel of the external source.
 3. The method of claim 1, whereinautomatically adjusting the backup schedule further comprises:responsive to the noted change being an increase in the distress statelevel of the external source, performing at least one of increasing anamount of content to backup or retaining executed backups for longerperiods of time.
 4. The method of claim 1, wherein automaticallyadjusting the backup schedule further comprises: responsive to the notedchange being a decrease in the distress state level of the externalsource, performing at least one of decreasing an amount of content tobackup or retaining executed backups for shorter periods of time.
 5. Themethod of claim 1, wherein automatically adjusting the backup schedulefurther comprises: responsive to the noted change further being anindication that the distress state level of the external source hasreached a critical point, executing an immediate backup of content bythe backup system.
 6. The method of claim 1, wherein monitoring thedistress state level of the external source comprises: receiving ane-mail from the external source regarding the distress state level orreading data from the external source concerning the distress statelevel.
 7. The method of claim 1, wherein the change to the distressstate level of the external source further comprises a non-securitythreat including at least one of a computing resource overloadassessment of the external source or an external software stabilityassessment of the external source.
 8. The method of claim 1, whereinautomatically adjusting the backup schedule further comprises: adjustingparameters controlling the backup system to tie an allocation ofresources devoted to the backup system on the first computer to ananticipated need for the resources.
 9. A non-transitory computerreadable storage medium comprising executable program code of a databackup manager that manages a backup system on a first computer, theprogram code when executed causing the data backup manager to performsteps comprising: monitoring via a network, by the data backup manageron the first computer, a distress state level of an external source thatis distinct from the backup system on the first computer that backs updata stored on the first computer, the distress state level of theexternal source monitored by the data backup manager based on anotification received from the external source, wherein the externalsource is executed on a second computer that is distinct from the firstcomputer that includes the data backup manager, the second computer doesnot back up the data stored on the first computer; noting, by the databackup manager on the first computer, a change to the distress statelevel of the external source indicating a security threat at theexternal source based on the monitored distress state level of theexternal source; automatically adjusting, by the data backup manager onthe first computer, a backup schedule of the backup system on the firstcomputer based on the noted change to the external distress state levelof the external source indicating the security threat at the externalsource, wherein the adjusting the backup schedule comprises adjusting anamount of content on the first computer to back up based on the notedchange to the external distress state level of the external source; andperforming, by the data backup manager on the first computer, a backupof the data stored on the first computer according to the adjustedbackup schedule.
 10. The non-transitory computer-readable storage mediumof claim 9, wherein automatically adjusting the backup schedule furthercomprises: adjusting a frequency of backing up content on the backupsystem based on the distress state level of the external source.
 11. Thenon-transitory computer-readable storage medium of claim 9, whereinautomatically adjusting the backup schedule further comprises:responsive to the noted change being an increase in the distress statelevel of the external source, performing at least one of increasing anamount of content to backup or retaining executed backups for longerperiods of time.
 12. The non-transitory computer-readable storage mediumof claim 9, wherein automatically adjusting the backup schedule furthercomprises: responsive to the noted change being a decrease in thedistress state level of the external source, performing at least one ofdecreasing an amount of content to backup or retaining executed backupsfor shorter periods of time.
 13. The non-transitory computer-readablestorage medium of claim 9, wherein automatically adjusting the backupschedule further comprises: responsive to the noted change further beingan indication that the distress state level of the external source hasreached a critical point, executing an immediate backup of content bythe backup system.
 14. The non-transitory computer-readable storagemedium of claim 9, wherein monitoring the distress state level of theexternal source comprises: receiving an e-mail from the external sourceregarding the distress state level or reading data from the externalsource concerning the distress state level.
 15. A first computer systemcomprising: a computer processor; and a non-transitory computer-readablestorage medium comprising executable code of a data backup manager thatmanages a backup system on the first computer system, the program codewhen executed causing the data backup manager to perform stepscomprising: monitoring via a network, by the data backup manager on thefirst computer system, a distress state level of an external source thatis distinct from the backup system on the first computer system thatbacks up data stored on the first computer system, the distress statelevel of the external source monitored by the data backup manager basedon a notification received from the external source, wherein theexternal source is executed on a second computer system that is distinctfrom the first computer system that includes the data backup manager,the second computer system does not back up the data stored on the firstcomputer system; noting, by the data backup manager on the firstcomputer system, a change to the distress state level of the externalsource indicating a security threat at the external source based on themonitored distress state level of the external source; automaticallyadjusting, by the data backup manager on the first computer system, abackup schedule of the backup system on the first computer system basedon the noted change to the external distress state level of the externalsource indicating the security threat at the external source, whereinthe adjusting the backup schedule comprises adjusting an amount ofcontent on the first computer system to back up based on the notedchange to the external distress state level of the external source; andperforming, by the data backup manager on the first computer, a backupof the data stored on the first computer according to the adjustedbackup schedule.
 16. The computer system of claim 15, whereinautomatically adjusting the backup schedule further comprises: adjustinga frequency of backing up content on the backup system based on thedistress state level of the external source.
 17. The computer system ofclaim 15, wherein automatically adjusting the backup schedule furthercomprises: responsive to the noted change being an increase in thedistress state level of the external source, performing at least one ofincreasing an amount of content to backup or retaining executed backupsfor longer periods of time.
 18. The computer system of claim 15, whereinautomatically adjusting the backup schedule further comprises:responsive to the noted change being a decrease in the distress statelevel of the external source, performing at least one of decreasing anamount of content to backup or retaining executed backups for shorterperiods of time.
 19. The computer system of claim 15, whereinautomatically adjusting the backup schedule further comprises:responsive to the noted change further being an indication that thedistress state level of the external source has reached a criticalpoint, executing an immediate backup of content by the backup system.20. The computer system of claim 15, wherein monitoring the distressstate level of the external source comprises: receiving an e-mail fromthe external source regarding the distress state level or reading datafrom the external source concerning the distress state level.